📖 Add the check Dangerous-Workflow #1341
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2.Fix the typo of rubygems
naveensrinivasan
approved these changes
Nov 27, 2021
asraa
reviewed
Nov 29, 2021
| @@ -356,6 +357,7 @@ CI-Tests | Does the project run tests in CI, e.g. [GitHub Act | |||
| CII-Best-Practices | Does the project have a [CII Best Practices Badge](https://bestpractices.coreinfrastructure.org/en)? | |||
| Code-Review | Does the project require code review before code is merged? | |||
| Contributors | Does the project have contributors from at least two different organizations? | |||
| Dangerous-Workflow | Does the project have GitHub Action workflows avoid dangerous patterns? | |||
There was a problem hiding this comment.
nit:
"Does the project have GitHub Action workflows that avoid dangerous patterns?"
|
Integration tests success for |
naveensrinivasan
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2.Fix the typo of rubygems
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs update
What is the current behavior? (You can also link to an open issue here)
✨ Add dangerous workflow check with untrusted code checkout pattern #1168
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: